Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1051

reference
687-tree-1
name
1051
tree-preservation-order

undefined

687-tpo-1
uprn
address-text
point
POINT (-1.018077 50.881767)
geometry
MULTIPOLYGON (((-1.018034 50.881763,-1.018036 50.881771,-1.018042 50.881779,-1.018051 50.881785,-1.018063 50.881789,-1.018076 50.881790,-1.018089 50.881789,-1.018101 50.881785,-1.018111 50.881779,-1.018117 50.881772,-1.018119 50.881763,-1.018117 50.881755,-1.018111 50.881748,-1.018102 50.881742,-1.018090 50.881738,-1.018077 50.881736,-1.018064 50.881737,-1.018052 50.881741,-1.018042 50.881747,-1.018036 50.881754,-1.018034 50.881763)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL